ENH: Improve error handling in Excel export functionality #62867
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…t- Added support for CSS-like font-weight properties in Excel exports- Enhanced font weight conversion for both xlsxwriter and openpyxl- Improved style inheritance and merging- Added support for header_bold parameter in Excel export- Maintained backward compatibility with existing code
|
It seems like this is just about the entire diff from #62670, not just the changes regarding error filtering. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
@rhshadrach
What this PR does
This PR enhances error handling and input validation in the Excel export functionality, making it more robust and user-friendly.
Key Changes
Error Handling:
Input Validation:
Code Quality:
Backward Compatibility
Related Issues
Part of the improvements from #62670